Distributed promotion management

ABSTRACT

Technologies are provided herein for distributed promotion management. According to a method for distributed promotion management, a device identification may be provided by a consumer electronic device that may comprise a dispensing device. An event notification may be received at the consumer electronic device. The event notification may be based upon the provided device identification. A promotional screen may then be displayed. The promotional screen may comprise a limited time offer section displaying a limited time offer. The limited time offer may be based on the received event notification.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims the benefit of U.S. Provisional Application No.62/055,925, filed Sep. 26, 2014, the entire contents of which are herebyincorporated by reference herein.

TRADEMARKS

COCA-COLA® is a registered trademark of The Coca-Cola Company, Atlanta,Ga., U.S.A. Other names, symbols, designs, or logos used herein may beregistered trademarks, trademarks, or product names of The Coca-ColaCompany or other companies.

BACKGROUND

A beverage dispenser is a device that dispenses carbonated soft drinkscalled fountain drinks. They may be found in restaurants, concessionstands, and other locations such as convenience stores. A beveragedispenser combines flavored syrup or syrup concentrate and carbondioxide with chilled water to make soft drinks. The syrup may be pumpedfrom a special container called a bag-in-box (BIB).

SUMMARY

This Summary is provided to introduce a selection of concepts in asimplified form that may be further described below in the DetailedDescription. This Summary is not intended to be used to limit the scopeof the claimed subject matter.

According to embodiments, distributed promotion management may beprovided. First, a device identification may be provided by a consumerelectronic device that may comprise a dispensing device. Then, an eventnotification may be received at the consumer electronic device. Theevent notification may be based upon the provided device identification.A promotional screen may then be displayed. The promotional screen maycomprise a limited time offer section displaying a limited time offer.The limited time offer may be based on the received event notification.

According to embodiments, distributing software from a softwaredistribution system may be provided. First, a record of attributes foreach device in a plurality of devices may be maintained and a group ofsoftware modules may be maintained. Then a first plurality of softwaremodules may be distributed to a first device within the plurality ofdevices. The first plurality of software modules may be selected fromthe group of software modules based on attributes associated with thefirst device. And a second plurality of software modules may bedistributed to a second device within the plurality of devices. Thesecond plurality of software modules may be selected from the group ofsoftware modules based on attributes associated with the second device.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this disclosure, illustrate various embodiments of the presentdisclosure. In the drawings:

FIG. 1 shows a block diagram of a network architecture;

FIG. 2 shows a block diagram of a network architecture;

FIG. 3 shows a dispensing device;

FIG. 4 is a flow chart setting forth the general stages involved in amethod for providing distributed promotion management;

FIG. 5 shows a user interface;

FIG. 6A shows a user interface;

FIG. 6B shows a camera view;

FIG. 7 shows a promotional screen;

FIG. 8 shows a system configuration screen;

FIG. 9 shows a security screen;

FIG. 10A shows a consumer engagement screen;

FIG. 10B shows a consumer engagement screen;

FIG. 11 shows a software distribution system;

FIG. 12 shows a software distribution system;

FIG. 13 shows a control architecture;

FIG. 14 shows a mobile computing environment; and

FIG. 15 shows an electronic device.

DETAILED DESCRIPTION

The following detailed description refers to the accompanying drawings.Wherever possible, the same reference numbers are used in the drawingsand the following description to refer to the same or similar elements.While embodiments of the disclosure may be described, modifications,adaptations, and other implementations are possible. For example,substitutions, additions, or modifications may be made to the elementsillustrated in the drawings, and the methods described herein may bemodified by substituting, reordering, or adding stages to the disclosedmethods. Accordingly, the following detailed description does not limitthe disclosure. Instead, the proper scope of the disclosure is definedby the appended claims.

Distributed promotion management may be provided. Consistent withembodiments, a user may read a device ID from a consumer electronicdevice (e.g. a beverage dispenser, kiosk, ATM, etc.) with a mobiledevice. The mobile device may send the device ID along with a user ID toa server in a notification from the mobile device. Using the user ID,the server may look up user preferences from a table on the server.Consistent with embodiments, rather than looking the user preferences upon the server, the user preferences may be sent from the mobile deviceto the server. The server may send the user preferences to the consumerelectronic device that corresponds to the device ID. In response, theconsumer electronic device may display a promotional screen based uponthe user preferences.

FIG. 1 shows a network architecture 100 for facilitating anindividualized interaction between a mobile computing device and anelectronic device. As shown in FIG. 1, network architecture 100 mayinclude a mobile computing device 102, a consumer electronic device 104,and a server 106. Mobile computing device 102 may be utilized by a user108 and may be in communication with consumer electronic device 104 andserver 106. The aforementioned network architecture for facilitating anindividualized interaction between a mobile computing device and anelectronic device may be described in related patent application U.S.Ser. No. 61/860,634 entitled “Facilitating Individualized UserInteraction with an Electronic Device,” filed on Jul. 31, 2013, thedisclosure of which is incorporated herein, in its entirety, byreference.

Computing device 102 may include a computing device application 110, auser ID 112, preference data 114, a scanner/camera 116, a mobilecomputing device wireless interface 118, and a near field communication(NFC) reader 120. Computing device 102 may comprise, but is not limitedto, a smartphone, a tablet computer, or a laptop computer that may becapable of executing one or more software application programs, such asapplication 110. Computing device 102 may be practiced in a computingenvironment 1400 described below with respect to FIG. 14.

Consumer electronic device 104 may comprise a consumer electronic devicewireless interface 122 and a display 124 that may provide personalizedcontent 126. Consumer electronic device 104 may further comprise adevice ID 128, a consumer electronic device application 130, an NFC tag132, and a bar code 134. Bar code 134 may comprise any machine-readableobject (e.g. one-dimensional (1-D) or two-dimensional (2-D)) that mayprovide data relating to consumer electronic device 104. Consumerelectronic device 104 may be practiced in an operating environment suchas an electronic device 1500 as described with respect to FIG. 15.

Server 106 may comprise a server application 136 and a table 138. Table138 may store preference data 114 related to user ID 112. Server 106 maybe practiced in an operating environment such as electronic device 1500as described with respect to FIG. 15.

Scanner/camera 116 and may be capable of short range wirelesscommunication via wireless interface 118. Wireless interface 118 may beconfigured to provide short range wireless communications via, but notlimited to, NFC, BLUETOOTH wireless technology, and Wi-Fi. Preferencedata 114 may also be stored on server 106 or in a database accessiblevia server 106 and cross-referenced (e.g. via table 138) with user ID112. User ID 112 may comprise an ID for user 108 of mobile computingdevice 102. Preference data 114 may comprise preferences associated withuser 108. For example, preference data 114 may comprise a list of user108's favorite beverages, games, products, and/or restaurants, a list ofuser 108's custom beverage mixes, and/or other information that can beused to personalize user 108's interaction with consumer electronicdevice 104.

Application 110 may be configured to send user ID 112 and preferencedata 114 along with device ID 128 (e.g. retrieved from consumerelectronic device 104) in a notification 140 to server 106 forconducting an individualized or unique interaction with consumerelectronic device 104. Notification 140 may only include user ID 112 anddevice ID 128. Upon receipt of device ID 128 and user ID 112, server 106may obtain and communicate preference data 114 (e.g. or a subsetthereof) to consumer electronic device 104.

Upon receiving device ID 128, server 106 may determine that mobiledevice 102 (and hence user 108 of mobile device 102) may be proximate toconsumer electronic device 104. Depending on how device ID 128 isobtained (e.g. scanning a barcode from consumer electronic device 104 orreading an NFC tag associated with consumer electronic device 104),server 106 may further determine that user 108 is addressing or isotherwise ready to commence interaction with consumer electronic device104. This may be opposed to user 108 being in line to use consumerelectronic device 104, but not yet being ready to commence interactionwith consumer electronic device 104.

Device ID 128 may be retrieved without establishing a communicationsession between mobile device 102 and consumer electronic device 104.For example, device ID 128 may be retrieved by using scanner/camera 116in conjunction with application 110 to scan a barcode (e.g. a 1-D or 2-Dbarcode) or other symbol encoded with device ID 128 on consumerelectronic device 104 (or displayed on display 124.) In other words, thebarcode or other symbol may be rendered on display 124 of consumerelectronic device 104, or printed, embossed, shown on a sticker, orotherwise made visible on one or more surfaces of consumer electronicdevice 104.

Device ID 128 may be retrieved by NFC reader 120 reading device ID 128from NFC tag 132. NFC tag 132 may be a passive or an active NFC tag thatmay store device ID 128. NFC tag 30 may comprise an RFID tag where theID associated with the RFID tag may comprise device ID 128. NFC tag 132may be placed inside a cabinet containing consumer electronic device 104at a location such that NFC reader 120 on mobile computing device 102may still read NFC tag 132. By placing NFC tag 132 inside the cabinet,NFC tag 132 may be protected from tampering.

Device ID 128 may be retrieved by initiating a communication sessionbetween mobile computing device 102 and consumer electronic device 104.For example, mobile computing device 102 may communicate via a wirelesscommunication session (e.g. between mobile computing device wirelessinterface 118 and consumer electronic device wireless interface 122)with consumer electronic device 104 using BLUETOOTH wireless technology,Wi-Fi or other wireless communication standards or technologies.

Consistent with embodiments, preference data 114 may be communicateddirectly from mobile computing device 102 to consumer electronic device104 via a communications session between mobile computing devicewireless interface 118 and consumer electronic device wireless interface122. For example, application 110 may pass preference data 114 toapplication 130 upon establishment of a communications session. Consumerelectronic device 104 may comprise a computing device capable ofexecuting one or more software application programs such as application130. Consumer electronic device 104 may also be configured to provideany number of consumer services and/or products, including, withoutlimitation, the dispensing of food and/or beverage products, videogaming services, video services, advertisement services, financialservices, etc. Consumer electronic device 104 may include fountain orpost-mix beverage dispensing machines, vending machines, public gamingdevices, automated teller machines or any other electronic device orkiosk configured to provide consumer products and/or services.

Similar to wireless interface 118 in mobile computing device 102,wireless interface 122 in consumer electronic device 104 may beconfigured to provide short range wireless communications via NFC,BLUETOOTH wireless technology, Wi-Fi or other wireless technologies.Consumer electronic device 104 may be utilized to display personalizedcontent 126 to user 108 based on preference data 114. For example,personalized content 126 may include a selection of user 108's favoritebeverages that may be available for purchase, advertisements targetedtowards user 108's favorite products, etc.

Device ID 128 may comprise a unique identification of consumerelectronic device 104. Device ID 128 may be utilized for identifyingconsumer electronic device 104 among other similar devices in a network.Application 130 may be configured to send device ID 128 to mobilecomputing device 102 in response to a communication session initiated byuser 108. As discussed above, the communication session may comprise ashort range wireless communication session during which device ID 128may be sent to mobile computing device 102. For example, device ID 128may be encoded in an unpowered NFC tag 132 that may be affixed toconsumer electronic device 104. Device ID 128 may be communicated whenuser 108 touches or brings mobile computing device 102 in closeproximity with NFC tag 132.

Device ID 128 may comprise stored data on consumer electronic device 104and may be communicated in response to a data request made by user 108during a Wi-Fi or BLUETOOTH wireless technology session with mobilecomputing device 102. In addition, the communication session maycomprise a scanning session initiated by user 108. For example, deviceID 128 may be encoded in a 1-D or 2-D barcode (e.g. a QR code) or othersymbol that may be either physically affixed to consumer electronicdevice 104 or displayed by consumer electronic device 104 on display124.

Application 130, executing on consumer electronic device 104, may beconfigured to receive an event notification 142 from server 106. Eventnotification 142 may include, for example, user ID 112 and preferencedata 114. Event notification 142 may be sent after user ID 112, deviceID 128, and preference data 114 are received by server 106.Communication between application 130 on consumer electronic device 104and application 136 on server 106 may be configured to utilize a serverpush technique in which a communication session (i.e. a server push 144)may be initiated and established by consumer electronic device 104 priorto user 108's interaction with consumer electronic device 104. Serverpush technology may include, but is not limited to, long polling, Comet,web sockets or Berkeley socket (“BSD”) techniques. Server 106 may holdthe sending of a response to data requests from consumer electronicdevice 104 until the requested data is available or a predeterminedtimeout event has occurred. Upon user ID 112 and preference data 114being received by consumer electronic device 104, application 130 may beconfigured to display personalized content 126 for user 108 on display124.

Server 106, which may be in communication with mobile computing device102 and consumer electronic device 104, may comprise a computing devicecapable of executing one or more software application programs such asapplication 136. Communication between server 106, mobile computingdevice 102, and consumer electronic device 104 may take place viarespective device network connections (not shown) over a wide areanetwork, such as the Internet. Server 106 may comprise a non-blockingsocket input/output server platform that may utilize a server pushtechnology (e.g. long polling or web sockets) where consumer electronicdevice 104 may initiate a network connection (e.g. server push 144) withserver 106 and keeps it open.

An example of a non-blocking socket input/output server platform maycomprise the ELASTIC COMPUTE CLOUD (“EC2”) web service (that maycomprise an “infrastructure as a service” cloud computing platform)provided by AMAZON.COM, INC. of Seattle, Wash. The EC2 web service mayfurther be utilized with Tornado that may comprise an open sourcescalable, non-blocking web server and web application framework.Embodiments of the disclosure may also be practiced in conjunction withother non-blocking socket servers and/or platforms from other providersand further, is not limited to any particular application, system, orplatform.

Application 136 may be configured to receive user ID 112 and preferencedata 114 contained in notification 140 from mobile computing device 102via an HTTP Application Programming Interface (“API”). Application 136may receive user ID 112 and use table 138 to look up correspondingpreference data 114. Application 136 may further be configured to serverpush communications to consumer electronic device 104. Application 136may also be configured to delay the sending of responses to the HTTPrequests from consumer electronic device 104 until the occurrence of oneof a timeout or the receipt of notification 140.

FIG. 2 shows network architecture 100 for facilitating an individualizedinteraction between mobile computing device 102 and consumer electronicdevice 104. Network architecture 100 includes mobile computing device102 including user ID 112 and, optionally, preference data 114. Mobilecomputing device 102 may be in active communication with consumerelectronic device 104 via BLUETOOTH wireless technology, Wi-Fi or otherwireless standards or technologies. Consumer electronic device 104,which may store device ID 128, may receive user ID 112 (and optionally,preference data 114) from mobile computing device 102. Consumerelectronic device 104 may then send device ID 128 to server 106 andreceive optional preference data 114 from server 106. Server 106 maystore table 138 that may include one or more user IDs 112 and,optionally, one or more instances of preference data 114. As discussedabove with respect to FIG. 1, preference data 114 may becross-referenced (e.g. via table 138) with user ID 112.

FIG. 3 shows a dispensing device 300. Consumer electronic device 104 maycomprise, but is not limited to, dispensing device 300. As shown in FIG.3, dispensing device 300 may comprise various beverage bases or beveragebase components such as beverage bases 305, 310, 315, and 320 as well asflavors (i.e. flavoring agents, flavor concentrates, or flavor syrups)325, 330, 335, and 340. Dispensing device 300 may further comprise otheringredients 345, an application 350, and a graphical user interface(GUI) 355. The aforementioned dispensing device may be described inrelated patent application U.S. Ser. No. 61/877,549 entitled “ProductCategorization User Interface for a Dispensing Device,” filed on Sep.13, 2013, the disclosure of which is incorporated herein, in itsentirety, by reference.

Beverage bases 305, 310, 315, and 320 may be concentrated syrups.Beverage bases 305, 310, 315, and 320 may be replaced with oradditionally provided with beverage base components. Each of beveragebases 305, 310, 315, and 320 or beverage base components and each offlavors 325, 330, 335, and 340 may be separately stored or otherwisecontained in individual removable cartridges that may be stored indispensing device 300.

Dispensing device 300 may identify the cartridges upon installation by auser or the user may be prompted to identify the cartridges when theyare installed. The aforementioned beverage components (i.e. beveragebases or beverage base components and flavors) may be combined, alongwith other beverage ingredients 345, to dispense various beverages orblended beverages (i.e. finished beverage products) from dispensingdevice 300. Dispensing device 300 may also be configured to dispensebeverage components individually. Dispensing device 300 may beconfigured to dispense beverage base components to form a beverage base.Other ingredients 345 may include diluents such as still or carbonatedwater, functional additives, or medicaments, for example. Otheringredients 345 may be installed in dispensing device 300, pumped todispensing device 300, or both. The carbonated water may be produced indispensing device 300 through mixing of CO2 and still water such as in acarbonator or other device that produces carbonated water.

Application 350 may be configured to generate GUI 355 on a displayscreen (not shown) of the dispensing device 300. GUI 355 may be utilizedto select and individually dispense one or more beverages fromdispensing device 300. The beverages may be dispensed as beveragecomponents in a continuous pour operation where one or more selectedbeverage components continue to be dispensed while a pour input isactuated by a user or in a batch pour operation whereby a predeterminedvolume of one or more selected beverage components are dispensed (e.g.one ounce at a time).

GUI 355 on dispensing device 300 may be addressed via a number ofmethods to select and dispense beverages. For example, the user mayinteract with GUI 355 via touch input to navigate one or more menus fromwhich to select and dispense a beverage. As another example, the usermay type in a code using an onscreen or physical keyboard (not shown) ondispensing device 300 to navigate one or more menus from which to selectand dispense a beverage. As yet another example, the user (e.g. user108) may use mobile computing device 102 to scan a one ortwo-dimensional barcode (e.g., a QR code) or other symbol shown on a tagor sticker affixed to, printed on dispensing device 300 or displayed ona display (e.g. GUI 355) of the dispensing device 300 to select abeverage for dispensing.

FIG. 4 is a flow chart setting forth the general stages involved in amethod 400 consistent with an embodiment of the disclosure for providingdistributed promotion management. Method 400 may be implemented usingnetwork architecture 100 as described above with respect to FIG. 1, FIG.2, and FIG. 3. Ways to implement the stages of method 400 will bedescribed in greater detail below.

Method 400 may begin at starting block 405 and proceed to stage 410where consumer electronic device 104 may provide device identification128. For example, application 130 may display a user interface 500 ondisplay 124. As shown in FIG. 5, user interface 500 may be utilized forselecting a menu associated with different product categories that maybe dispensed from consumer electronic device 104. User interface 500 mayinclude a main menu of product categories 505, 510, 515, 520 and 525that may be selected by user 108. Each of the aforementioned categoriesmay correspond to various product categories such as all of a number ofbeverage brands available on consumer electronic device 104 (e.g.product category 505), a caffeine-free beverage category (e.g. productcategory 510), a featured category associated with beverages tied to oneor more promotional or advertising campaigns (e.g. product category515), a flavor category in which beverages are organized correspondingto a particular fruit flavor or other particular flavor additiveavailable on consumer electronic device 104 (e.g. product category 520),and a low-calorie beverage category (e.g. product category 525).

User interface 500 may also include a Help user control 530 that may beselected by user 108 to review instructions for selecting and dispensinga product from consumer electronic device 104. User interface 500 mayalso include a language toggle user control 535 that may be selected byuser 108 to change the language utilized. User interface 500 may alsoinclude a bar code 540 that may comprise a one or two-dimensionalbarcode (e.g. a QR code) or other symbol that may be utilized by user108 to uniquely identify consumer electronic device 104 so as to enablea customized interaction or enable user 108 to remotely access consumerelectronic device 104 from mobile computing device 102. Theaforementioned consumer customized interactions and remote access tasksare described in related patent application U.S. Ser. No. 61/863,269entitled “Dynamically Adjusting Ratios of Beverages in a MixedBeverage,” filed on Aug. 7, 2013, the disclosure of which isincorporated herein, in its entirety, by reference. User interface 500may also include a user control 550 for directly accessing a product(e.g. water) from the main menu of product categories 505-525. Usercontrol 550 may be utilized by a consumer who only wishes to quicklydispense a product without having to navigate through one or more ofproduct categories 505-525.

From stage 410, where consumer electronic device 104 provides deviceidentification 128 (e.g. in bar code 540), method 400 may advance tostage 420 where consumer electronic device 104 may receive an eventnotification (e.g. event notification 142) based upon provided deviceidentification 128. For example, user 108 may cause application 110 toexecute on mobile computing device 102. As a result, application 110 maycause a user interface 605 to be displayed on mobile computing device102 as shown in FIG. 6A. User interface 605 may include a plurality ofuser options including, but not limited to, a connect option 610.

From user interface 605, user 108 may select connect option 610. Inresponse to user 108 selecting connect option 610, application 110 maycause a camera view 615 to be displayed on mobile computing device 102as shown in FIG. 6B. While in camera view 615, user 108 may pointscanner/camera 116 at user interface 500 to cause bar code 540 to bedisplayed within camera view 615. Once bar code 540 is within cameraview 615, user 108 may cause scanner/camera 116 to capture an image ofbar code 540. Once the image of bar code 540 is captured, application110 may process the captured image of bar code 540 to extract device ID128 stored within bar code 540. As described above with respect to FIG.1, in response, mobile computing device 102 may send notification 140 toserver 106 that may in turn send event notification 142 to consumerelectronic device 104. As stated above, event notification 142 mayinclude user ID 112 and preference data 114.

Once consumer electronic device 104 receives event notification 142based upon provided device identification 128 in stage 420, method 400may continue to stage 430 where consumer electronic device 104 maydisplay, in response to receiving event notification 142, a promotionalscreen 700 on display 124. Promotional screen 700 may comprise a limitedtime offer (LTO) section 705. Limited time offer section 705 may bebased on received event notification 142. Consistent with embodiments ofthe disclosure, limited time offer section 705 may only be displayedwithin promotional screen 700 when individualized interaction betweenmobile computing device 102 and electronic device 104 has beenestablished as described above with respect to FIG. 1.

In addition to limited time offer section 705, promotional screen 700may comprise a custom mixes section 710, a favorites section 715, and arecommended section 720. Each of limited time offer section 705, custommixes section 710, favorites section 715, and recommended section 720may include one or more user selectable elements, when selected by user108, may cause consumer electronic device to dispense a beverage thatmay correspond to the selected user selectable element.

User selectable elements in limited time offer section 705 maycorrespond to beverages, brands, or beverage recipes that may bedesignated by an operator of consumer electronic device 104. Userselectable elements in limited time offer section 705 may correspond tobeverages that may or may not comprise brand offerings. User selectableelements in limited time offer section 705 may correspond to mixes ofone or more brand offerings, beverage bases, beverage base components,flavors, diluents, and/or sweeteners. For example, the operator ofconsumer electronic device 104 may comprise a movie theater that ispromoting a particular movie. Consequently, a user selectable element inlimited time offer section 705 may correspond to a beverage related tothe promoted movie. In particular, a user selectable element in limitedtime offer section 705 may correspond to a beverage related to abeverage consumed in the promoted movie. As another example, theoperator of consumer electronic device 104 may comprise a restaurantthat is promoting a particular food offering. Consequently, a userselectable element in limited time offer section 705 may correspond to abeverage related to the promoted food offering. In particular, a userselectable element in limited time offer section 705 may correspond to abeverage that may enhance or otherwise be related to the promoted foodoffering.

Additionally, according to some implementations of the technologiespresented herein, user selectable elements in limited time offer section705 may correspond to user selectable items comprising selecting a newdrink or beverage mix, sending a drink or beverage recipe to a friend,redeeming a coupon, and/or activating/initializing a loyalty rewardredemption. Furthermore, some user selectable items that can beimplemented as a limited time offer may include interactive activitiessuch as, for example, playing an interactive game such as “guess thatmix” whereby a user attempts to differentiate one or more flavors orbrands in a particular recipe. Additional interactive activities caninclude taking a quiz whereby a user submits one or more answers toquestions displayed to the user, and/or learning a fun fact whereby auser is presented interesting information or other information relatedto a limited time offer or fact from the past.

User selectable elements in custom mixes section 710 may correspond tobeverage recipes that user 108 may have designed or otherwise obtained.In other words, user selectable elements in custom mixes section 710 maycorrespond to beverages that may not comprise brand offerings, but maycomprise mixes of one or more brand offerings, beverage bases, beveragebase components, flavors, diluents, and/or sweeteners. Recipes forbeverages displayed in custom mixes 710 may be stored and obtained byconsumer electronic device 104 from preference data 114.

User selectable elements in favorites section 715 may correspond tobrand beverage offerings that user 108 may select most often or hasother wise designated as favorite beverages. The identification ofbeverages displayed in favorites section 715 may be stored in preferencedata 114.

User selectable elements in recommended section 720 may correspond tobeverage offerings that an operator of consumer electric device wishesto offer or otherwise suggest that user 108 consume. The recommendedbeverage offerings corresponding to recommended section 720 may bedetermined or otherwise calculated based upon user 108's custom mixesand favorites identified in preference data 114. For example,application 130 (running on consumer electronic device 104) orapplication 136 (running on server 106) may run a recommendation processthat may calculate beverage recommendations for recommended section 720based upon user 108's preference data 114 (e.g. user 108's custom mixesand/or favorites.) After consumer electronic device 104 displays, inresponse to receiving event notification 142, promotional screen 700 instage 430, method 400 may then end at stage 440.

Consistent with embodiments of the disclose, the operator of consumerelectronic device 104 may be able to select when promotional screen 700may be displayed on display 124 and/or which sections of user interface700 may be displayed on display 124. For example, the choices providedby promotional screen 700 may cause potential users of consumerelectronic device 104 to backup and have to wait. This may causebusiness issues for the operator of consumer electronic device 104 whomay wish to turn off the ability for consumer electronic device 104 toprovide promotional screen 700. Or the operator of consumer electronicdevice 104 may wish to turn off the ability for consumer electronicdevice 104 to provide promotional screen 700 during certain time periodsand to turn on the ability for consumer electronic device 104 to providepromotional screen 700 during other time periods. For example, foron-peak time periods, the operator may wish to turn off promotionalscreen 700 in order to improve operational efficiency. However, duringoff-pear time periods, the operator may wish to turn on promotionalscreen 700 because it may drive business in because consumers may wishto engage with promotional screen 700.

In order to select when and/or how promotional screen 700 may bedisplayed on display 124, the operator of consumer electronic device 104may navigate to a system configuration screen 800 as shown in FIG. 8.From system configuration screen 800, the operator of consumerelectronic device 104 may navigate through a security screen 900 shownin FIG. 9 to a consumer engagement screen 1000 shown in FIG. 10A. Atconsumer engagement screen 1000, the operator may select disable all CEfunctions 1005, which may cause application 130 not to display promotionscreen 700. In addition, selecting disable all CE functions 1005 maycause application 130 not to display bar code 540 in user interface 500.Consumer engagement screen 1000 may allow the operator of consumerelectronic device 104 to select times of the day to enable or disableall CE functions.

Consumer engagement screen 1000 may allow the operator to select whereto run the aforementioned recommendation process for calculatingbeverage recommendations for recommended section 720. For example, ifthe operator selects dispenser side recommendations 1010, theaforementioned recommendation process may run on consumer electronicdevice 104. Or if the operator leaves dispenser side recommendations1010 unselected, the aforementioned recommendation process may run onserver 106.

Consumer engagement screen 1000 may allow the operator to select certainsections of promotion screen 700 to disable or enable. The operator mayselect custom mixes 1015, which may allow custom mixes section 710 to bedisplayed on promotional screen 700. In addition, the operator mayselect favorites 1020, which may allow favorites section 715 to bedisplayed on promotional screen 700. Furthermore, the operator mayselect limited time offer 1025, which may allow limited time offersection 705 to be displayed on promotional screen 700. Moreover, theoperator may select none 1030, which may disable limited time offersection 705, custom mixes section 710, and favorites section 715 frombeing displayed on promotional screen 700. Consumer engagement screen1000 may allow the operator of consumer electronic device 104 to selecttimes of the day to enable or disable limited time offer section 705,custom mixes section 710, favorites section 715, and/or recommendedsection 720. Application 130 may display an indicia 1035 (e.g. a QRcode) on display 124 to indicate that consumer electronic device 104 isconnected to server 106. Application 130 may not display indicia 1035when consumer electronic device 104 is not connected to server 106. FIG.10B shows a consumer engagement screen 1050 that may be similar toconsumer engagement screen 1000. As shown in FIG. 10B, consumerengagement screen 1050 may include a mixes and favorites 1055 selection.Mixes and favorites 1055 may combine the aforementioned functionality ofcustom mixes 1015 and favorites 1020 as described above with respect toFIG. 10A.

In addition, consumer engagement screen 1050 may include an active LTOconfiguration box 1060. As stated above, promotional screen 700 maycomprise a limited time offer section 705 having user selectableelements corresponding to a limited time offer. Consistent withembodiments of the disclosure, one or more limited time offer may bedisplayed on promotional screen 700. Each limited time offer may havecorresponding one of more user selectable elements that may correspondto beverages for example. Active LTO configuration box 1060 may list oneor more limited time offers. Promotional screen 700 may display the oneor more limited time offers selected by the operator from the one ormore limited time offers listed in active LTO configuration box 1060.

Server 106 may push the one or more limited time offers to consumerelectronic device 104. The one or more limited time offers maycorrespond to a particular time period (e.g. quarter of a year.) Thenthe operator of consumer electronic device 104 may determine which ofthe one or more limited time offers the operator wishes to display inpromotional screen 700 by making one or more selections within activeLTO configuration box 1060. The process described above with respect toFIG. 8, FIG. 9, FIG. 10A, and FIG. 10B may, in addition to beingperformed locally at consumer electronic device 104, may be performedremotely (e.g. from server 106.)

FIG. 11 shows a software distribution system 1100 for distributingsoftware to consumer electronic devices such as consumer electronicdevice 104. As shown in FIG. 11, software distribution system 1100 maycomprise a device management server 1105, a network 1110, a firstcollection of devices 1115, and a second collection of devices 1120.Device management server 1105 may be practiced in an operatingenvironment such as electronic device 1500 as described with respect toFIG. 15. Network 1110 may comprise any network capable of transportingdata such as, for example, the Internet.

Device management server 1105 may update, store, and distribute aplurality of software collections. The plurality of software collectionsmay comprise, but are not limited to, a first software collection 1125and a second software collection 1130. The plurality of softwarecollections may comprise any number of software collections and is notlimited to two. First software collection 1125 may comprise a pluralityof software modules comprising, for example, a first collectionoperating system 1135, a first collection recipe management system 1140,a first collection content management system 1145, and first collectionconfiguration parameters 1150. Second software collection 1105 maycomprise a plurality of software modules comprising, for example, asecond collection operating system 1155, a second collection recipemanagement system 1160, a second collection content management system1165, and second collection configuration parameters 1170. Configurationparameters may comprise, but are not limited to: i) show/hide water; ii)soft/hard ice; iii) consumer engagement on/off; and iv) enable/disablepromotions. Software modules may comprise, but are not limited to: i) anoperating system; ii) a recipe management system; and iii) a contentmanagement system.

First collection of devices 1115 may comprise a first plurality ofconsumer electronic devices such as, but not limited to, a firstcollection first consumer electronic device 1175, a first collectionsecond consumer electronic device 1180, and a first collection thirdconsumer electronic device 1185. Each of the first plurality of consumerelectronic devices may comprise, but are not limited to, consumerelectronic device 104. Second collection of devices 1120 may comprise asecond plurality of consumer electronic devices such as, but not limitedto, a second collection first consumer electronic device 1190 and asecond collection second consumer electronic device 1195. Each of thesecond plurality of consumer electronic devices may comprise, but arenot limited to, consumer electronic device 104. Each of first collectionof devices 1115 and second collection of devices 1120 may comprise anynumber of consumer electronic devices.

Consumer electronic devices within first collection of devices 1115 andsecond collection of devices 1120 may have attributes. These attributesmay comprise, but are not limited to: i) a customer ID for an operatorof the consumer electronic device; ii) a chain ID (e.g. movie theaterbrand, a restaurant brand, etc.) for an operator of the consumerelectronic device; iii) a location (e.g. country) of the consumerelectronic device; iv) a language for the consumer electronic device;and v) an equipment type of the consumer electronic device.Consequently, consumer electronic devices within system 1100 may beseparated into mutually exclusive groups (e.g. first collection ofdevices 1115 and second collection of devices 1120) based on desiredattributes associated with each group.

Each device within first collection of devices 1115 may have a first setof attributes that may be the same for each device within firstcollection of devices 1115. Accordingly, software to run each devicewithin first collection of devices 1115 may be the same. Moreover, eachdevice within second collection of devices 1120 may have a second set ofattributes that may be the same for each device within second collectionof devices 1120. Accordingly, software to run each device within secondcollection of devices 1120 may be the same. Consequently, first softwarecollection 1125 may be maintained on device management server 1105 fordistribution to each device within first collection of devices 1115.Similarly, second software collection 1130 may be maintained on devicemanagement server 1105 for distribution to each device within secondcollection of devices 1120.

FIG. 12 shows a software distribution system 1200 for distributingsoftware to consumer electronic devices such as consumer electronicdevice 104. As shown in FIG. 12, software distribution system 1200 maycomprise a device management server 1205, a network 1210, and aplurality of devices 1215. Device management server 1205 may bepracticed in an operating environment such as electronic device 1500 asdescribed with respect to FIG. 15. Network 1210 may comprise any networkcapable of transporting data such as, for example, the Internet.

Device management server 1205 may update, store, and distribute aplurality of software modules selected from a group of software moduleson device management server 1205. The plurality of software modules maycomprise, but are not limited to, a first operating system 1235, a firstrecipe management system 1240, a first content management system 1245,and first configuration parameters 1250. The plurality of softwaremodules may further comprise a second operating system 1255, a secondrecipe management system 1260, a second content management system 1265,and second configuration parameters 1270.

Plurality of devices 1215 may comprise, but are not limited to, a firstconsumer electronic device 1275, a second consumer electronic device1280, a third consumer electronic device 1285, and a forth consumerelectronic device 1290. Each of plurality of devices 1215 may comprise,but are not limited to, consumer electronic device 104. Plurality ofdevices 1215 may comprise any number of devices and is not limited tofour.

In software distribution system 1100 of FIG. 11, all software modulesmay be maintained in collections (e.g. first software collection 1125and second software collection 1130) and may be sent out in collections.However, in device management system 1200 of FIG. 12, all softwaremodules may be maintained individually and may be sent out in aindividually. Furthermore, in contrast with system 1100, plurality ofdevices 1215 may not be placed into mutually exclusive groups. Ratherdevice management system 1200 may maintain a record of attributes foreach device in plurality of devices 1215 and, based on a device'sattributes, distribute software modules accordingly. For example, basedon it's desired attributes, first consumer electronic device 1275 may besent first operating system 1235, second recipe management system 1260,first content management system 1245, and second configurationparameters 1270. Similarly, based on it's desired attributes, secondconsumer electronic device 1280 may be sent first operating system 1235,first recipe management system 1240, first content management system1245, and first configuration parameters 1250. In addition, based onit's desired attributes, third consumer electronic device 1285 may besent second operating system 1255, second recipe management system 1260,second content management system 1265, and second configurationparameters 1270. And based on it's desired attributes, forth consumerelectronic device 1290 may be sent second operating system 1255, firstrecipe management system 1240, second content management system 1265,and first configuration parameters 1250.

FIG. 13 shows a control architecture 1300 that may be used to control,for example, dispensing device 300 of FIG. 3. As shown in FIG. 13,control architecture 1300 may comprise a core dispense module (CDM)1304, a human machine interface (HMI) module 1306, a user interface (UI)1308, and a machine bus (MBUS) 1310. HMI 1306 may connect to orotherwise interface and communicate with at least one external device(e.g. mobile computing device 102) being external to dispensing device300. HMI 1306 may also control and update display screens on UI 1308.CDM 1304 may control flows from a plurality of pumps and/or valves 1312in dispensing device 300 according to a recipe to mix and dispense aproduct (e.g. a beverage) from dispensing device 300.

Beverage components (i.e. beverage bases or beverage base components andflavors) may be combined, along with other ingredients, to dispensevarious products that may include beverages or blended beverages (i.e.finished beverage products) from dispensing device 300. However,dispensing device 300 may also be configured to dispense beveragecomponents individually. Dispensing device 300 may be configured todispense beverage base components to form a beverage base or finishedbeverage. The other beverage ingredients may include diluents such asstill or carbonated water, functional additives, or medicaments, forexample.

An example of control architecture 1300 for dispensing device 300 may bedescribed in U.S. Patent Application Ser. No. 61/987,020, titledDispenser Control Architecture, filed on May 1, 2014, the entirety ofwhich is hereby incorporated by reference. MBUS 1310 may facilitatecommunication between HMI module 1306 and CDM 1304. HMI module 1306,MBUS 1310, and CDM 1304 may collectively comprise common corecomponents, implemented as hardware or as combination of hardware andsoftware, which may be adapted to provide customized functionality indispensing device 300. Dispensing device 300 may further include memorystorage and a processor. Examples of UI 1308 may be described in U.S.Patent Application Ser. No. 61/877,549, titled Product CategorizationUser Interface for a Dispensing Device, filed on Sep. 13, 2013, theentirety of which is hereby incorporated by reference.

UI 1308 may detect what area of a touch screen has been touched by auser (e.g. user 108.) In response, UI 1308 may send HMI module 1306 dataregarding where the touch screen was touched. In response, HMI module1306 may interpret this received data to determine whether to have UI1308 display a different UI screen or to issue a command to CDM 1304.For example, HMI module 1306 may determine that the user touched aportion of the touch screen corresponding to a beverage brand. Inresponse, HMI module 1306 may issue a command to CDM 1304 to pour thecorresponding beverage brand. Or HMI module 1306 may determine that theuser touched a portion of the touch screen corresponding to a requestfor another screen. In response, HMI module 1306 may cause UI 1308 todisplay the requested screen.

In some embodiments, UI 1308 in dispensing device 300 may be utilized toselect and individually dispense one or more beverages. The beveragesmay be dispensed as beverage components in a continuous pour operationwhereby one or more selected beverage components continue to bedispensed while a pour input is actuated by a user or in a batch pouroperation where a predetermined volume of one or more selected beveragecomponents are dispensed (e.g. one ounce at a time). UI 1308 may beaddressed via a number of methods to select and dispense beverages. Forexample, a user may interact with UI 1308 via touch input to navigateone or more menus from which to select and dispense a beverage. Asanother example, a user may type in a code using an onscreen or physicalkeyboard (not shown) on dispensing device 300 to navigate one or moremenus from which to select and dispense a beverage.

UI 1308, which may include a touch screen and a touch screen controller,may be configured to receive various commands from a user (i.e. consumerinput) in the form of touch input, generate a graphics output and/orexecute one or more operations with dispensing device 300 (e.g. via HMImodule 1306 and/or CDM 1304), in response to receiving theaforementioned commands. A touch screen driver in HMI module 1306 may beconfigured to receive the consumer or customer inputs and generateevents (e.g. touch screen events) that may then be communicated througha controller to an operating system of HMI module 1306.

Dispensing device 300 may be in communication with one or more externaldevice (e.g. mobile computing device 102). In some embodiments, thecommunication between dispensing device 300 and the external device maybe accomplished utilizing any number of communication techniquesincluding, but not limited to, near-field wireless technology such asBLUETOOTH, Wi-Fi and other wireless or wireline communication standardsor technologies, via a communication interface.

FIG. 14 shows a mobile computing environment 1400 that mobile computingdevice 102 may operate within. For example, mobile computing environment1400 may comprise, but is not limited to, a smartphone, a tabletpersonal computer, or a laptop computer. Mobile computing environment1400 may comprise a handheld computer having both input elements andoutput elements. Input elements may include touch screen display 1405that may allow the user to enter information into mobile computingenvironment 1400, a microphone 1415, and a camera 1420. Mobile computingenvironment 1400 may incorporate additional input elements such as aphysical keypad (not shown). A soft keypad (not shown) may also begenerated on touch screen display 1405.

Touch screen display 1405 on mobile computing environment 1400 may alsocomprise an output element that can display a graphical user interface(GUI). Other output elements include a speaker 1410. Additionally,mobile computing environment 1400 may incorporate a vibration module(not shown), which may cause mobile computing environment 1400 tovibrate to notify the user of an event. Mobile computing environment1400 may incorporate a headphone jack (not shown) for providing outputsignals.

Mobile computing environment 1400 may comprise a number of othercomponents. The components may include a processor 1425, a memory 1430,radio functions 1435, an accelerometer 1440, and a GPS receiver 1445.Memory 430 may be utilized for storing an operating system 1450 and mayinclude a data storage 1455. Memory 1430 may also include a number ofapplications 1460 including, but not limited to, a mobile phoneapplication, a data processing application, a calculator, games, anInternet browser, navigation a camera/video application and otherapplications such as application 110 that may be utilized forfacilitating an individualized interaction with consumer electronicdevice 104 as discussed above. Radio functions 1435 may support shortrange wireless communications via NFC, BLUETOOTH wireless technology,Wi-Fi or other wireless technologies. Radio functions 1435 may also beutilized to connect to the Internet (or other types of networks) as wellas to remote computing systems.

FIG. 15 shows electronic device 1500 that may provide an operatingenvironment for consumer electronic device 104 or server 106 forexample. Electronic device 1500 may comprise a computing device that mayinclude at least one processing unit 1502 and a system memory 1504.Depending on the configuration and type of computing device, systemmemory 1504 may comprise, but is not limited to, volatile (e.g. randomaccess memory (RAM)), non-volatile (e.g. read-only memory (ROM)), flashmemory, or any combination. System memory 1504 may include an operatingsystem 1505 and other applications 1518. Operating system 1505 may besuitable for controlling electronic device 1500's operation.

Electronic device 1500 may have additional features or functionality.For example, electronic device 1500 may also include additional datastorage devices (not shown) that may be removable and/or non-removablesuch as, for example, magnetic disks, optical disks, solid state storagedevices (SSD), flash memory or tape. Electronic device 1500 may alsohave input device(s) 1512 such as a keyboard, a mouse, a pen, a soundinput device (e.g., a microphone), a touch input device, etc. Outputdevice(s) 1514 such as a display, speakers, a printer, etc. may also beincluded. The aforementioned devices are examples and others may beused. Communication connection(s) 1516 may also be included and utilizedto connect to the Internet (or other types of networks) as well as toremote computing systems.

Embodiment, for example, may be implemented as a computer process(method), a computing system, or as an article of manufacture, such as acomputer program product or computer readable media. The computerprogram product may be a computer storage media readable by a computersystem and encoding a computer program of instructions for executing acomputer process.

Computer readable media may include computer storage media. Computerstorage media may include volatile and nonvolatile, removable andnon-removable media implemented in any method or technology for storageof information (such as computer readable instructions, data structures,program modules, or other data) in hardware. System memory 1504 (as wellas memory 1430) may be an example of computer storage media (e.g. memorystorage.) Computer storage media may include, but is not limited to,RAM, ROM, electrically erasable read-only memory (EEPROM), flash memoryor other memory technology, CD-ROM, digital versatile disks (DVD) orother optical storage, magnetic cassettes, magnetic tape, magnetic diskstorage or other magnetic storage devices, or any other medium that canbe used to store information.

Computer readable media may also include communication media.Communication media may be embodied by computer readable instructions,data structures, program modules, or other data in a modulated datasignal, such as a carrier wave or other transport mechanism, andincludes any information delivery media. Modulated data signal maydescribe a signal that may have one or more characteristics set orchanged in such a manner as to encode information in the signal.Communication media may include wired media such as a wired network ordirect-wired connection, and wireless media such as acoustic, radiofrequency (RF), infrared, and other wireless media.

A beverage may include, but is not limited to, pulp and pulp-free citrusand non-citrus fruit juices, fruit drink, vegetable juice, vegetabledrink, milk, soy milk, protein drink, soy-enhanced drink, tea, water,isotonic drink, vitamin-enhanced water, soft drink, flavored water,energy drink, coffee, smoothies, yogurt drinks, hot chocolate andcombinations thereof. The beverage may also be carbonated ornon-carbonated. The beverage may comprise beverage components (e.g.,beverage bases, colorants, flavorants, and additives).

A beverage base may comprise parts of the beverage or the beverageitself prior to additional colorants, additional flavorants, and/oradditional additives. Beverage bases may include, but are not limited tosyrups, concentrates, and the like that may be mixed with a diluent suchas still or carbonated water or other diluent to form a beverage. Thebeverage bases may have reconstitution ratios of about 3:1 to about 6:1or higher. Beverage bases may comprise a mixture of beverage basecomponents.

A beverage base component may be included in beverage bases. Thebeverage base component may comprise parts of beverages that may beconsidered food items by themselves. The beverage base components may bemicro-ingredients such as an acid portion of a beverage base, anacid-degradable and/or non-acid portion of a beverage base, natural andartificial flavors, flavor additives, natural and artificial colors,nutritive or non-nutritive natural or artificial sweeteners, additivesfor controlling tartness (e.g. citric acid or potassium citrate),functional additives such as vitamins, minerals, or herbal extracts,nutraceuticals, or medicaments. The micro-ingredients may havereconstitution ratios from about 10:1, 20:1, 30:1, or higher with manyhaving reconstitution ratios of 50:1 to 300:1. The viscosities of themicro-ingredients may range from about 1 to about 100 centipoise.

Thus, for the purposes of requesting, selecting, or dispensing abeverage base, a beverage base formed from separately stored beveragebase components may be equivalent to a separately stored beverage base.For the purposes of requesting, selecting or dispensing a beverage, abeverage formed from separately stored beverage components may beequivalent to a separately stored beverage.

Separately stored may comprise that the components may be kept separateuntil combined. For instance, the components may be separately storedindividually in a container or package or instead may be all stored inone container or package wherein each component is individually packaged(e.g. plastic bags) so that they do not blend while in the container orpackage. The container or package, itself, may be individual, adjacentto, or attached to another container or package. A blended beverage mayinclude final products wherein two or more beverages have been blendedor mixed or otherwise combined to form a final product.

The product ingredients may include beverage bases or beverage basecomponents (e.g., concentrated syrups) as well as flavors (i.e.,flavoring agents, flavor concentrates, or flavor syrups), which may beseparately stored or otherwise contained in individual removablecontainers. Each of the beverage bases or beverage base components andeach of the flavors may be separately stored or otherwise contained inindividual removable containers, cartridges, packages or the like thatmay generally be referred to simply as a package or ingredients package.

Embodiments are described above with reference to block diagrams and/oroperational illustrations of methods, systems, and computer programproducts. The operations/acts noted in the blocks may be skipped oroccur out of the order as shown in any flow diagram. For example, two ormore blocks shown in succession may be executed substantiallyconcurrently or the blocks may sometimes be executed in the reverseorder, depending upon the functionality/acts involved.

While the specification includes examples, the disclosure's scope isindicated by the following claims. Furthermore, while the specificationhas been described in language specific to structural features and/ormethodological acts, the claims are not limited to the features or actsdescribed above. Rather, the specific features and acts described aboveare disclosed as example for embodiments.

What is claimed is:
 1. A method comprising: providing a deviceidentification, the device identification identifying a first consumerelectronic device; receiving, at the first consumer electronic device,an event notification based upon the provided device identification; anddisplaying, at the first consumer electronic device and in response toreceiving the event notification, a promotional screen comprising alimited time offer section displaying a limited time offer, the limitedtime offer being based on the received event notification.
 2. The methodof claim 1, further comprising: displaying, at the first consumerelectronic device, a consumer engagement screen configured to solicitinput data for configuring the promotional screen; receiving input datain response to the displayed consumer engagement screen; and displayingthe promotional screen configured according to the received input data.3. The method of claim 2, wherein the received input data is receivedfrom an operator of the first consumer electronic device, and whereinthe event notification comprises a user identification (ID) andpreference data associated with a user.
 4. The method of claim 1,wherein the device identification comprises a machine-readable object.5. The method of claim 4, further comprising displaying themachine-readable object on the consumer electronic device.
 6. The methodof claim 1, wherein the device identification comprises amachine-readable object provided on a display of the consumer electronicdevice.
 7. The method of claim 1, wherein the consumer electronic devicecomprises a beverage dispensing device.
 8. The method of claim 1,wherein the event notification comprises a user identification (ID) andpreference data.
 9. The method of claim 8, wherein the user ID andpreference data is associated with a user providing the deviceidentification.
 10. The method of claim 1, wherein displaying thepromotional screen comprises displaying the promotional screen onlyduring a predetermined time period.
 11. The method of claim 10, whereinthe predetermined time period comprises an on peak time period for anoperator of the consumer electronic device.
 12. A method comprising:soliciting input data through a consumer engagement user interface forconfiguring a promotional screen; receiving input data in response tothe soliciting input data for configuring the promotional screen; anddisplaying, at a consumer electronic device, the promotional screenconfigured according to the received input data.
 13. The method of claim12, further comprising: providing a device identification at theconsumer electronic device, the device identification identifying theconsumer electronic device; receiving, at the consumer electronicdevice, an event notification based upon the provided deviceidentification; and displaying, at the consumer electronic device and inresponse to receiving the event notification, the promotional screen.14. The method of claim 13, wherein the consumer engagement userinterface comprises data configured to cause the promotional screen toinclude a recommended section corresponding to beverage offerings thatan operator of the consumer electric device desires to offer.
 15. Themethod of claim 13, wherein the consumer engagement user interfacecomprises data configured to cause the promotional screen to include afavorites section corresponding to beverage offerings that a userindicated as the user's favorite beverages.
 16. The method of claim 13,wherein the consumer engagement user interface comprises data configuredto cause the promotional screen to include a custom mixes sectioncorresponding to beverage offerings for user-provided recipes.
 17. Themethod of claim 13, wherein the consumer engagement user interfacecomprises data configured to cause the promotional screen to include alimited time offer section corresponding to beverage offerings that anoperator of the consumer electric device desires to promote for limitedtime.
 18. The method of claim 13, wherein the consumer engagement userinterface comprises displaying an indicia indicating a connectionbetween a consumer electronic device and a server.
 19. The method ofclaim 13, wherein displaying the consumer engagement user interfacesolicits input data for determining where to calculate recommendedbeverage offerings to include in a recommended section on thepromotional screen.
 20. A beverage dispenser device, the beveragedispenser device being configured to perform operations to: display aconsumer engagement screen configured to solicit input data forconfiguring a promotional screen; receive input data in response to thedisplayed consumer engagement screen; provide a device identificationbased on the received input data indicating that the deviceidentification is to be provided, the device identification identifyingthe beverage dispenser; receive an event notification based upon theprovided device identification; and display, in response to receivingthe event notification, a promotional screen comprising a limited timeoffer section displaying a limited time offer, the limited time offerbeing based on the received event notification.